Skip to content

Build/Test Tools: Remove the unused Gutenberg e2e test script. - #15624

Closed
desrosj wants to merge 1 commit into
WordPress:trunkfrom
desrosj:remove/tests-gutenberg
Closed

Build/Test Tools: Remove the unused Gutenberg e2e test script.#15624
desrosj wants to merge 1 commit into
WordPress:trunkfrom
desrosj:remove/tests-gutenberg

Conversation

@desrosj

@desrosj desrosj commented Nov 6, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

This removes tests/gutenberg/, which was added in r48382 (#50469) to run Gutenberg's end-to-end tests against a Core checkout. The script was never added to an npm script or a CI workflow, and it no longer works:

  • It crashes on startup. chalk v5+ is ESM-only, so require( 'chalk' ).bold is undefined and the script throws at line 51. That has been true since chalk was updated past v4.
  • The Gutenberg branch it checks out is gone. It checks out Gutenberg's wp/trunk branch, and git ls-remote now only returns wp/latest.
  • The test command it runs no longer exists. It runs npm run test-e2e packages/e2e-tests/specs/editor. Gutenberg has no test-e2e script (it's now test:e2e, which runs Playwright), and packages/e2e-tests/specs was removed in early 2024 when the Puppeteer tests moved to Playwright (Migrate 'autosave' e2e tests to Playwright gutenberg#58171).
  • The Core build hook it relies on was already removed. It passes FORCE_REDUCED_MOTION=true to the Core build, but that webpack definition was removed in r56699.

Trac ticket: Core-65845.

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Investigating whether the script was still used, making the removal, and drafting the commit message and this description. I reviewed the changes.

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

🤖 Generated with Claude Code

@desrosj
Build/Test Tools: Remove the unused Gutenberg e2e test script.
2d124b6 
The `tests/gutenberg/run.js` script was introduced in [48382] to run the Gutenberg end-to-end tests against a WordPress Core checkout. It was never added to any npm script or CI workflow, and it no longer works:

- It clones and checks out Gutenberg's `wp/trunk` branch, which no longer exists.
- It runs `npm run test-e2e packages/e2e-tests/specs/editor`, but Gutenberg no longer has a `test-e2e` script, and the Puppeteer specs in `packages/e2e-tests/specs` were removed when its tests moved to Playwright.
- It fails before reaching any of those steps, because `chalk` v5+ is ESM-only and `require( 'chalk' ).bold` is `undefined`.

This removes the script and its `.wp-env.sample.json` file, along with the `chalk` and `uuid` dev dependencies, which were only added for and used by this script.

The other change in [48382], the `FORCE_REDUCED_MOTION` webpack definition, was already removed in [56699].
@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@desrosj
desrosj requested a review from a team November 6, 2026 04:15
@desrosj desrosj moved this from Backlog to In review in WordPress Project Build Tooling Nov 6, 2026
@desrosj
desrosj marked this pull request as ready for review November 6, 2026 04:15
@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props desrosj.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

  • @propsbot add <username> to give props to a GitHub user. Requires write access.
  • @propsbot remove <username> to leave a user out of the props. Requires write access.
  • @propsbot refresh to refresh this list. Adding the props-bot label works too.

@desrosj desrosj self-assigned this Nov 6, 2026
@desrosj

desrosj commented Nov 6, 2026

Copy link
Copy Markdown
Member Author

Merged in r65309.

@desrosj desrosj closed this Nov 6, 2026
@github-project-automation github-project-automation Bot moved this from In review to Done in WordPress Project Build Tooling Nov 6, 2026
@desrosj
desrosj deleted the remove/tests-gutenberg branch November 6, 2026 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@desrosj desrosj

Labels

None yet

Projects

WordPress Project Build Tooling
Status: Done

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@desrosj